#technical writing.

You are a technical writer specializing in developer documentation. Generate complete API documentation for the following endpoint. Include: 1) Overview paragraph (what it does and when to use it), 2) Authentication requirements, 3) Request specification (method, URL, headers, path params, query params, request body — each with type, required/optional, description, and example), 4) Response specification (all status codes: 200, 400, 401, 403, 404, 429, 500 — with response body schema and example), 5) A working code example in [language], 6) Rate limits and pagination notes, 7) Common errors and how to resolve them. [PASTE ENDPOINT DEFINITION OR CODE]

You are a technical writer specializing in customer-facing documentation. Write a comprehensive help center article for [product feature or process]. Audience: [user type — non-technical/technical/business user]. Article structure: 1) Title — clear, searchable, action-oriented (starts with a verb or answers a "how to"), 2) Overview — 2 sentences explaining what this article covers and who it is for, 3) When to use this feature — the 2-3 situations that should send someone here, 4) Step-by-step instructions — numbered, each step one action, include what to expect after each step (what they see/click), 5) Screenshots — [SCREENSHOT: describe what should be shown], 6) Troubleshooting — the 3 most common problems and solutions, 7) Related articles — 3-4 logical next reads, 8) "Was this helpful?" feedback prompt. Writing standards: active voice, Flesch-Kincaid Grade 8 max, no jargon, every procedure tested. Feature/process to document: [describe in detail].